
<html><HEAD>
<LINK REL=STYLESHEET HREF="default.css" TYPE="text/css">
<TITLE>
Database connections</TITLE>
</HEAD>
<BODY>

<!-- Header -->
<p class="ancestor" align="right"><A HREF="apptechp247.htm">Previous</A>&nbsp;&nbsp;<A HREF="apptechp249.htm" >Next</A>
<!-- End Header -->
<A NAME="BAJIGDCH"></A><h1>Database connections</h1>
<A NAME="TI6931"></A><p>If you are deploying an executable or component that accesses
a database, your users need access to the DBMS and to the database
your application uses. </p>
<p><img src="images/note.gif" width=17 height=17 border=0 align="bottom" alt="Note"> <span class=shaded>Where to install database connectivity files</span> <A NAME="TI6932"></A>You <i>do not need to deploy database connectivity
files</i> with a client application that relies on a middle-tier
component on another computer to perform database transactions.
Database connectivity files must be deployed on the computer that
interacts with the database server.</p>
<A NAME="TI6933"></A><p>You need to:<A NAME="TI6934"></A>
<ul>
<li class=fi>If necessary,
install the DBMS runtime (client) files in the application directory
or in a directory on the system path<br>
If your application uses a standalone SQL Anywhere database,
you can install the SQL Anywhere Runtime Edition files on the user's
computer. For more information, see <A HREF="apptechp248.htm#BGBDIGCC">"SQL Anywhere files"</A>. Otherwise follow the instructions
and licensing rules specified by the vendor.<br></li>
<li class=ds>Make sure each user has access to the database the
application uses<br>
If your application uses a local database, install the database
and any associated files, such as a log file, on the user's
computer.<br><br>
If your application uses a server database, make sure the
user's computer is set up to access the database. This
may be the task of a database administrator.<br></li>
<li class=ds>Install any database interfaces your application
uses on the user's computer</li>
<li class=ds>If your application uses the ODBC interface, configure
the ODBC database drivers and data sources, as described in <A HREF="apptechp248.htm#BGBDCJAI">"Configuring ODBC data
sources and drivers"</A>
</li>
</ul>
</p>
<A NAME="TI6935"></A><p>For more information about database drivers and interfaces,
see: <A NAME="TI6936"></A>
<ul>
<li class=fi><A HREF="apptechp248.htm#BGBEAAHB">"Native database drivers"</A></li>
<li class=ds><A HREF="apptechp248.htm#BGBCBACD">"ODBC database drivers and
supporting files"</A></li>
<li class=ds><A HREF="apptechp248.htm#BGBCFFEH">"OLE DB database providers"</A></li>
<li class=ds><A HREF="apptechp248.htm#CHDGJGJI">"ADO.NET database interface"</A></li>
<li class=ds><A HREF="apptechp248.htm#BGBCJHAF">"JDBC database interface"</A>
</li>
</ul>
</p>
<A NAME="BGBEAAHB"></A><h2>Native database drivers</h2>
<A NAME="TI6937"></A><p><A HREF="apptechp248.htm#BAJDEJJI">Table 37-6</A> lists
the native database drivers supplied with PowerBuilder. If an application
or component uses the database specified, the file is required on
the computer. The first two characters of the native database file
name are PB, the next three characters identify the database, and
the last two identify the version of PowerBuilder.</p>
<A NAME="BAJDEJJI"></A><table cellspacing=0 cellpadding=6 border=1 frame="void" rules="all"><caption>Table 37-6: PowerBuilder native database
drivers</caption>
<tr><th  rowspan="1"  ><A NAME="TI6938"></A>Name</th>
<th  rowspan="1"  ><A NAME="TI6939"></A>Required for</th>
</tr>
<tr><td  rowspan="1"  ><A NAME="TI6940"></A><i>pbin9115.dll</i></td>
<td  rowspan="1"  ><A NAME="TI6941"></A>INFORMIX I-Net 9</td>
</tr>
<tr><td  rowspan="1"  ><A NAME="TI6942"></A><i>pbo90115.dll</i></td>
<td  rowspan="1"  ><A NAME="TI6943"></A>Oracle9<i>i</i></td>
</tr>
<tr><td  rowspan="1"  ><A NAME="TI6944"></A><i>pbo10115.dll</i></td>
<td  rowspan="1"  ><A NAME="TI6945"></A>Oracle 10<i>g</i></td>
</tr>
<tr><td  rowspan="1"  ><A NAME="TI6946"></A><i>pbora115.dll</i></td>
<td  rowspan="1"  ><A NAME="TI6947"></A>Oracle 11<i>g</i></td>
</tr>
<tr><td  rowspan="1"  ><A NAME="TI6948"></A><i>pbsnc115.dll</i></td>
<td  rowspan="1"  ><A NAME="TI6949"></A>SQL Native Client for Microsoft SQL Server</td>
</tr>
<tr><td  rowspan="1"  ><A NAME="TI6950"></A><i>pbdir115.dll</i></td>
<td  rowspan="1"  ><A NAME="TI6951"></A>Sybase DirectConnect</td>
</tr>
<tr><td  rowspan="1"  ><A NAME="TI6952"></A><i>pbase115.dll</i></td>
<td  rowspan="1"  ><A NAME="TI6953"></A>Sybase Adaptive Server Enterprise CT-LIB
for Adaptive Server 15 only</td>
</tr>
<tr><td  rowspan="1"  ><A NAME="TI6954"></A><i>pbsyc115.dll</i></td>
<td  rowspan="1"  ><A NAME="TI6955"></A>Sybase Adaptive Server Enterprise CT-LIB </td>
</tr>
<tr><td  rowspan="1"  ><A NAME="TI6956"></A><i>pbsyj115.dll</i></td>
<td  rowspan="1"  ><A NAME="TI6957"></A>Sybase Adaptive Server Enterprise CT-LIB
for <ABBR title = "e a server" >EAServer</ABBR> deployment only</td>
</tr>
</table>
<p><b>Installed path</b>   <i>\Program Files\Sybase\Shared\PowerBuilder</i></p>
<p><b>Deployment path</b>   Same directory as the application, in a directory on the system
path, or in the <A HREF="apptechp244.htm#BGBCIHAF">App Path registry key</A>. </p>
<p><b>Registry entries</b>   See <A HREF="apptechp244.htm#BGBCIHAF">"App Path registry key"</A>.</p>
<p><b>Notes</b>   When you deploy a PowerBuilder custom class user object to <ABBR title = "e a server" >EAServer</ABBR>, you need to use the SYJ
database interface rather than SYC to connect to an Adaptive Server
Enterprise database. You cannot use SYJ in the PowerBuilder development
environment, but you can use the SYJ Database Profile Setup dialog
box to set the appropriate connection parameters. You can then copy
the syntax from the Preview tab into the script for your Transaction object.</p>
<A NAME="BGBCBACD"></A><h2>ODBC database drivers and supporting files</h2>
<A NAME="TI6958"></A><p>This section lists files that are required for all ODBC database
connections from PowerBuilder or InfoMaker applications, as well
as files required for a specific database interface or DBMS.</p>
<A NAME="TI6959"></A><h4>PowerBuilder ODBC interface files</h4>
<A NAME="TI6960"></A><p>The following PowerBuilder ODBC interface files are required
if your application uses ODBC:</p>
<A NAME="TI6961"></A><table cellspacing=0 cellpadding=6 border=1 frame="void" rules="all"><caption>Table 37-7: PowerBuilder ODBC interface files</caption>
<tr><th  rowspan="1"  ><A NAME="TI6962"></A>Name</th>
<th  rowspan="1"  ><A NAME="TI6963"></A>Description</th>
</tr>
<tr><td  rowspan="1"  ><A NAME="TI6964"></A><i>pbodb115.dll</i></td>
<td  rowspan="1"  ><A NAME="TI6965"></A>PowerBuilder ODBC interface</td>
</tr>
<tr><td  rowspan="1"  ><A NAME="TI6966"></A><i>pbodb115.ini</i></td>
<td  rowspan="1"  ><A NAME="TI6967"></A>PowerBuilder ODBC initialization file</td>
</tr>
</table>
<p><b>Installed path</b>   <i>\Program Files\Sybase\Shared\PowerBuilder</i></p>
<p><b>Deployment path</b>   Same directory as the application, in a directory on the system
path, or in the <A HREF="apptechp244.htm#BGBCIHAF">App Path registry key</A>. </p>
<p><b>Registry entries</b>   See <A HREF="apptechp244.htm#BGBCIHAF">"App Path registry key"</A>.</p>
<p><b>Notes</b>   The <i>PBODB115.INI</i> file must be in a directory
defined by the HKEY_CURRENT_USER\Software\Sybase\PowerBuilder\11.5\InitPath registry
setting or, in the absence of that key,  in the same directory as
the DLL file. In most cases, the target deployment machine will
not have the registry setting and, therefore, the INI file should
be in the same directory as the DLL.</p>
<A NAME="BGBCHJFB"></A><h4>Microsoft ODBC files</h4>
<A NAME="TI6968"></A><p><A HREF="apptechp248.htm#BAJFDBIF">Table 37-8</A> lists
the Microsoft ODBC files that are required if your application uses
ODBC.</p>
<A NAME="BAJFDBIF"></A><table cellspacing=0 cellpadding=6 border=1 frame="void" rules="all"><caption>Table 37-8: Microsoft ODBC files</caption>
<tr><th  rowspan="1"  ><A NAME="TI6969"></A>Name</th>
<th  rowspan="1"  ><A NAME="TI6970"></A>Description</th>
</tr>
<tr><td  rowspan="1"  ><A NAME="TI6971"></A><i>DS16GT.dll <br>DS32GT.dll<br>ODBC32.dll <br>ODBC32GT.dll<br>ODBCAD32.exe<br>ODBCCP32.cpl<br>ODBCCP32.dll <br>ODBCCR32.dll<br>ODBCINST.cnt <br>ODBCINST.hlp <br>ODBCINT.dll<br>ODBCTRAC.dll</i></td>
<td  rowspan="1"  ><A NAME="TI6972"></A>Microsoft ODBC driver manager, DLLs,
and Help files</td>
</tr>
</table>
<p><b>Installed path</b>   Windows system directory. </p>
<p><b>Deployment path</b>   Windows system directory.</p>
<p><b>Registry entries</b>   None.</p>
<p><b>Notes</b>   The Microsoft ODBC Driver Manager (<i>ODBC32.dll</i>)
and supporting files are usually already installed in the user's
Windows system directory. </p>
<A NAME="BGBDIGCC"></A><h4>SQL Anywhere files</h4>
<A NAME="TI6973"></A><p>If your PowerBuilder application uses a SQL Anywhere database,
you need to deploy the SQL Anywhere DBMS as well as SQL Anywhere's
ODBC database drivers. </p>
<p><img src="images/note.gif" width=17 height=17 border=0 align="bottom" alt="Note"> <span class=shaded>Restrictions</span> <A NAME="TI6974"></A>PowerBuilder includes SQL Anywhere for use during the development process.
However, this product cannot be deployed royalty-free to your users.</p>
<A NAME="TI6975"></A>If your application requires the data definition language
(DDL), a transaction log, stored procedures, or triggers, see your
Sybase sales representative.</p>
<A NAME="TI6976"></A><p>If your application uses a standalone database, you can deploy
the SQL Anywhere Desktop Runtime System to users' computers
without incurring additional license fees. The runtime system allows
the user to retrieve and modify data in the database, but does not
allow modifications to the database schema. It does not support
transaction logs, stored procedures, or triggers.</p>
<A NAME="TI6977"></A><p>A full installation for the SQL Anywhere driver, runtime engine,
and supporting files is available in the PowerBuilder setup program. <A HREF="apptechp248.htm#BAJGIECF">Table 37-9</A> lists
some of the files that are installed. For more information see the <i>RuntimeEdition.html</i>
 file
in the installed SQL Anywhere directory. It contains a list of all
the SQL Anywhere files that can be freely deployed with PowerBuilder
applications to end users' computers.</p>
<A NAME="BAJGIECF"></A><table cellspacing=0 cellpadding=6 border=1 frame="void" rules="all"><caption>Table 37-9: SQL Anywhere files</caption>
<tr><th  rowspan="1"  ><A NAME="TI6978"></A>Name</th>
<th  rowspan="1"  ><A NAME="TI6979"></A>Description</th>
</tr>
<tr><td  rowspan="1"  ><A NAME="TI6980"></A><i>dbodbc11.dll</i></td>
<td  rowspan="1"  ><A NAME="TI6981"></A>SQL Anywhere ODBC driver</td>
</tr>
<tr><td  rowspan="1"  ><A NAME="TI6982"></A><i>dbbackup.exe</i></td>
<td  rowspan="1"  ><A NAME="TI6983"></A>SQL Anywhere backup utility</td>
</tr>
<tr><td  rowspan="1"  ><A NAME="TI6984"></A><i>dbcon11.dll</i></td>
<td  rowspan="1"  ><A NAME="TI6985"></A>Connection dialog box, required if you
do not provide your own dialog box and your end users are to create their
own data sources, if they need to enter user IDs and passwords when
connecting to the database, or if they need to display the Connection
dialog box for any other purpose</td>
</tr>
<tr><td  rowspan="1"  ><A NAME="TI6986"></A><i>dbisqlc.exe</i></td>
<td  rowspan="1"  ><A NAME="TI6987"></A>Interactive SQL utility</td>
</tr>
<tr><td  rowspan="1"  ><A NAME="TI6988"></A><i>dblgen11.dll</i></td>
<td  rowspan="1"  ><A NAME="TI6989"></A>Language-specific string library (<i>EN</i> indicates
the English version)</td>
</tr>
<tr><td  rowspan="1"  ><A NAME="TI6990"></A><i>dblib11.dll</i></td>
<td  rowspan="1"  ><A NAME="TI6991"></A>Interface library</td>
</tr>
<tr><td  rowspan="1"  ><A NAME="TI6992"></A><i>dbtool11.dll</i></td>
<td  rowspan="1"  ><A NAME="TI6993"></A>SQL Anywhere database tools</td>
</tr>
<tr><td  rowspan="1"  ><A NAME="TI6994"></A><i>dbunlspt.exe</i></td>
<td  rowspan="1"  ><A NAME="TI6995"></A>SQL Anywhere unload utility</td>
</tr>
<tr><td  rowspan="1"  ><A NAME="TI6996"></A><i>dbvalid.exe</i></td>
<td  rowspan="1"  ><A NAME="TI6997"></A>SQL Anywhere validation utility</td>
</tr>
<tr><td  rowspan="1"  ><A NAME="TI6998"></A><i>rteng11.exe</i></td>
<td  rowspan="1"  ><A NAME="TI6999"></A>Restricted runtime engine</td>
</tr>
<tr><td  rowspan="1"  ><A NAME="TI7000"></A><i>rteng11.lic</i></td>
<td  rowspan="1"  ><A NAME="TI7001"></A>License file for restricted runtime engine</td>
</tr>
<tr><td  rowspan="1"  ><A NAME="TI7002"></A><i>dbctrs11.dll</i></td>
<td  rowspan="1"  ><A NAME="TI7003"></A>Performance utility</td>
</tr>
<tr><td  rowspan="1"  ><A NAME="TI7004"></A><i>dbserv11.dll</i></td>
<td  rowspan="1"  ><A NAME="TI7005"></A>Server utility</td>
</tr>
</table>
<p><b>Installed path</b>   <i>\Program Files\Sybase\SQL
Anywhere 11\bin32</i> or <i>\bin64</i></p>
<p><b>Deployment path</b>   Same directory as the application, in a directory on the system
path, or in the <A HREF="apptechp244.htm#BGBCIHAF">App Path registry key</A>. </p>
<p><b>Registry entries</b>   See <A HREF="apptechp244.htm#BGBCIHAF">"App Path registry key"</A> and <A HREF="apptechp248.htm#BGBDCJAI">"Configuring ODBC data
sources and drivers"</A>.</p>
<p><b>Privilege requirements on Vista</b>   When running under User Account Control, the SQL Anywhere
restricted runtime engine (<i>rteng11.exe</i>) and
other SQL Anywhere executables require elevated privileges. For
Windows Vista and later versions of Windows, you can use the SQL
Anywhere elevated operations agent (<i>dbelevate11.exe</i>)
to elevate the privileges of users running these executables and
allow non-elevated client processes to autostart elevated servers
or database engines. The following DLLs also require elevated privileges
when they are registered and unregistered: <i>dbcon11.dll</i>, <i>dbctrs11.dll</i>, <i>dbodbc11.dll</i>, <i>dboledb11.dll</i>,
and <i>dboledba11.dll</i>.</p>
<p><b>Notes</b>   Supporting files should be installed in the same directory
as <i>dbodbc11.dll</i>. If you are not using the English
string library, make sure you deploy the appropriate version of
the language-specific string library.</p>
<A NAME="BGBDCJAI"></A><h4>Configuring ODBC data
sources and drivers</h4>
<p><b>ODBC.INI</b>   To allow the user to connect to a particular data source,
your installation program must provide a definition for that data
source in the ODBC.INI key in the registry on the computer that
accesses the data source, in <i>HKEY_CURRENT_USER</i> for
a user DSN or in <i>HKEY_LOCAL_MACHINE</i> for a
system DSN. The data source definition specifies the name and location
of the database driver as well as the command required to start
the database engine. The data source in the ODBC Data Sources key
must also be listed in ODBC.INI.</p>
<A NAME="TI7006"></A><p>The following shows typical registry entries for a data source
called MyApp DB that uses SQL Anywhere. Registry keys are enclosed
in square brackets and are followed by string values for that key
in the format <FONT FACE="Courier New">"<i>Name</i>"="<i>Value</i>"</FONT>:<p><PRE> [HKEY_CURRENT_USER\SOFTWARE\ODBC\ODBC.INI\MyApp DB]<br>"Driver"="C:\Program Files\Sybase\SQL Anywhere 11\<br>   bin32\dbodbc11.dll"<br>"Start"="c:\program files\sybase\SQL Anywhere 11\bin32\<br>   rteng11.exe -c9m"<br>"UID"="dba"<br>"PWD"="sql"<br>"Description"="Database for my application"<br>"DatabaseFile"="C:\Program Files\myapps\myapp.db"<br>"AutoStop"="Yes"<br> <br><br>[HKEY_CURRENT_USER\SOFTWARE\ODBC\ODBC.INI\<br>   ODBC Data Sources]<br>"MyApp DB"="SQL Anywhere 11.0"</PRE></p>
<p><b>ODBCINST.INI</b>   Your installation program needs to make two types of entry
in the <i>ODBCINST.INI </i>key in <i>HKEY_LOCAL_MACHINE\SOFTWARE\ODBC</i> for
each driver that your deployed application uses:<A NAME="TI7007"></A>
<ul>
<li class=fi>Add
a string value with the name of the driver and the data value "Installed" to
the <i>ODBC DRIVERS</i> key in <i>ODBCINST.INI</i> </li>
<li class=ds>Add a new key for each driver to the<i> ODBCINST.INI</i> key
with string values for Driver and Setup<br>
Some drivers require additional string values in <i>ODBCINST.INI</i>.<br>
</li>
</ul>
</p>
<A NAME="TI7008"></A><p>If the ODBC database driver files are not located in a directory
on the system path, you also need to add their location to the App
Paths key for the executable file. </p>
<A NAME="TI7009"></A><p>If you are using ODBC drivers obtained from a vendor, you
can use the driver's setup program to install the driver
and create registry entries.</p>
<A NAME="TI7010"></A><p>The following shows a typical registry entry for SQL Anywhere.
A registry key is enclosed in square brackets and is followed by
string values for the key in the format <FONT FACE="Courier New"><i>"Name</i>"="<i>Value</i>"</FONT>:<p><PRE> [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\<br>   SQL Anywhere 11.0]<br>"Driver"="c:\program files\sybase\SQL Anywhere 11\<br>   bin32\dbodbc11.dll"<br>"Setup"="c:\program files\sybase\SQL Anywhere 11\<br>   bin32\dbodbc11.dll"</PRE></p>
<A NAME="TI7011"></A><p>For more information about the contents of
the registry entries for ODBC drivers and data sources, see <i>Connecting
to Your Database</i>
.</p>
<A NAME="BGBCFFEH"></A><h2>OLE DB database providers</h2>
<A NAME="TI7012"></A><p>If your application uses OLE DB to access data, you must install
Microsoft's Data Access Components software on each user's
computer if it is not installed already. </p>
<A NAME="TI7013"></A><p>The PowerBuilder OLE DB interface requires the functionality
of the Microsoft Data Access Components (MDAC) version 2.8 or higher
software. Version 2.8 is distributed with Windows XP Service Pack
2 and Windows Server 2003. </p>
<A NAME="TI7014"></A><p>To check the version of MDAC on a computer, users can download
and run the MDAC Component Checker utility from the <A HREF="http://msdn2.microsoft.com/en-us/data/aa937730.aspx">MDAC Downloads page</A>
.</p>
<A NAME="TI7015"></A><p>On the Windows Vista operating system, the Windows Data Access Components
(DAC) version 6.0 includes some changes to work with Vista but is
otherwise functionally equivalent to MDAC 2.8.</p>
<p><img src="images/note.gif" width=17 height=17 border=0 align="bottom" alt="Note"> <span class=shaded>OLE DB data providers installed with MDAC</span> <A NAME="TI7016"></A>Several Microsoft OLE DB data providers are automatically
installed with MDAC, including the providers for <ACRONYM title = "sequel" >SQL</ACRONYM> Server (SQLOLEDB) and ODBC (MSDASQL).</p>
<A NAME="TI7017"></A><h4>PowerBuilder OLE DB interface files</h4>
<A NAME="TI7018"></A><p>The PowerBuilder OLE DB interface file is required if your
application uses OLE DB. The ODBC initialization file is required
if you have used it to customize OLE DB settings:</p>
<A NAME="TI7019"></A><table cellspacing=0 cellpadding=6 border=1 frame="void" rules="all"><caption>Table 37-10: PowerBuilder OLE DB interface files</caption>
<tr><th  rowspan="1"  ><A NAME="TI7020"></A>Name</th>
<th  rowspan="1"  ><A NAME="TI7021"></A>Description</th>
</tr>
<tr><td  rowspan="1"  ><A NAME="TI7022"></A><i>pbole115.dll</i></td>
<td  rowspan="1"  ><A NAME="TI7023"></A>PowerBuilder OLE DB interface</td>
</tr>
<tr><td  rowspan="1"  ><A NAME="TI7024"></A><i>pbodb115.ini</i></td>
<td  rowspan="1"  ><A NAME="TI7025"></A>PowerBuilder ODBC initialization file </td>
</tr>
</table>
<p><b>Installed path</b>   <i>\Program Files\Sybase\Shared\PowerBuilder</i></p>
<p><b>Deployment path</b>   Same directory as the application, in a directory on the system
path, or in the <A HREF="apptechp244.htm#BGBCIHAF">App Path registry key</A>. </p>
<p><b>Registry entries</b>   See <A HREF="apptechp244.htm#BGBCIHAF">"App Path registry key"</A>.</p>
<p><b>Notes</b>   The INI and DLL files must be in the same directory. If you
have modified the <i>pbodb115</i> initialization file,
make sure you deploy the modified version.</p>
<A NAME="CHDGJGJI"></A><h2>ADO.NET database interface</h2>
<A NAME="TI7026"></A><p>The PowerBuilder ADO.NET interface supports the OLE DB, Microsoft
SQL Server .NET, Oracle ODP.NET, and Sybase ASE data providers.
If you use ADO.NET, you must deploy <i>pbado115.dll</i>,<i> pbrth115.dll</i>, <i>Sybase.PowerBuilder.Db.dll</i>, <i>Sybase.PowerBuilder.DbExt.dll</i>,
and, for OLE DB, the OLE DB data provider.</p>
<A NAME="TI7027"></A><p>The files <i>pbado115.dll</i> and<i> pbrth115.dll</i> are
standard DLL files, and you can deploy them in the same way as other
PowerBuilder DLLs. However, <i>Sybase.PowerBuilder.Db.dll</i> and <i>Sybase.PowerBuilder.DbExt.dll</i> are
.NET assemblies. You can use one of three techniques to deploy the
files:<A NAME="TI7028"></A>
<ul>
<li class=fi>Deploy <i>Sybase.PowerBuilder.Db.dll</i> and <i>Sybase.PowerBuilder.DbExt.dll</i> in
the same directory as the executable file that calls the ADO.NET
driver.</li>
<li class=ds>Use a .NET application configuration file to assign
the path of <i>Sybase.PowerBuilder.Db.dll</i> and <i>Sybase.PowerBuilder.DbExt.dll</i>.
The file contains configuration settings that the common language
runtime (CLR) reads as well as settings that the application reads.
For an executable file, the configuration file has the same name
as the executable file with the extension .<i>config</i>.
The <i>pb115.exe.config</i> file in your PowerBuilder
11.5 directory is an example. <br>
For more information about configuration files, see the Microsoft
Visual Studio SDK documentation.<br></li>
<li class=ds>Add the <i>Sybase.PowerBuilder.Db.dll</i> and <i>Sybase.PowerBuilder.DbExt.dll</i> assemblies
to the Global Assembly Cache (GAC). For more information about the
GAC, see the section on the Global Assembly Cache in the Microsoft
Visual Studio SDK documentation. If you use the Runtime Packager,
the assemblies are installed in the GAC.
</li>
</ul>
</p>
<A NAME="BGBCJHAF"></A><h2>JDBC database interface</h2>
<A NAME="TI7029"></A><p>The PowerBuilder JDB interface supports the Sun Java Runtime
Environment (JRE) versions 1.2 and later. </p>
<A NAME="TI7030"></A><p>If your application or component uses JDBC connections, you
must deploy the JDB driver as well as the appropriate Java package
for the Java VM you are using. The Java virtual machine and a vendor-supplied
JDBC-compliant driver, such as Sybase jConnect&#174; for JDBC,
must also be installed and configured on the computer that accesses
the data source. </p>
<A NAME="TI7031"></A><p>For more information about the Java VM, see <A HREF="apptechp249.htm#BAJBFFIA">"Java support"</A>.</p>
<A NAME="TI7032"></A><table cellspacing=0 cellpadding=6 border=1 frame="void" rules="all"><caption>Table 37-11: PowerBuilder JDB files</caption>
<tr><th  rowspan="1"  ><A NAME="TI7033"></A>Name</th>
<th  rowspan="1"  ><A NAME="TI7034"></A>Description</th>
</tr>
<tr><td  rowspan="1"  ><A NAME="TI7035"></A><i>pbjdb115.dll</i></td>
<td  rowspan="1"  ><A NAME="TI7036"></A>PowerBuilder JDBC Driver (JDB) for JRE
1.2 or later</td>
</tr>
<tr><td  rowspan="1"  ><A NAME="TI7037"></A><i>pbjdbc12115.jar</i></td>
<td  rowspan="1"  ><A NAME="TI7038"></A>Java package for PowerBuilder JDB driver
and JRE 1.2 or later</td>
</tr>
</table>
<p><b>Installed path</b>   <i>\Program Files\Sybase\Shared\PowerBuilder</i></p>
<p><b>Deployment path</b>   Same directory as the application, in a directory on the system
path, or in the <A HREF="apptechp244.htm#BGBCIHAF">App Path registry key</A>. </p>
<p><b>Registry entries</b>   Make sure the CLASSPATH environment variable includes the
PowerBuilder <i>pbjdbc12115.jar</i> file. For example:<p><PRE> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control</PRE><PRE>     \Session Manager\Environment]</PRE><PRE> "CLASSPATH"="C:\Program Files\sybase\shared\</PRE><PRE>     PowerBuilder\pbjdbc12115.jar;...</PRE></p>
<p><b>Notes</b>   See <A HREF="apptechp253.htm#BGBBJEIE">"PowerBuilder components
on <ABBR title = "e a server" >EAServer</ABBR> "</A> and <A HREF="apptechp254.htm#BGBDJAHI">"Web DataWindow on <ABBR title = "e a server" >EAServer</ABBR> "</A>.</p>

